Skip to content

fix: assert default-no confirmation in Hermes removal test - #10557

Open
texasich wants to merge 1 commit into
omacom:quattrofrom
texasich:fix-hermes-removal-default-no-test
Open

fix: assert default-no confirmation in Hermes removal test#10557
texasich wants to merge 1 commit into
omacom:quattrofrom
texasich:fix-hermes-removal-default-no-test

Conversation

@texasich

@texasich texasich commented Sep 6, 2026

Copy link
Copy Markdown

Adds an assertion that the Hermes data-removal prompt passes
--default=false to gum confirm.

The existing stub declines the prompt regardless of its arguments,
so removing the flag previously went undetected.

Validation:

  • All 16 focused checks pass.
  • Removing --default=false makes the new assertion fail.
  • Production code is unchanged.

Follow-up to #10271.

Signed-off-by: texasich <texasich@gmail.com>
@smfworks

Copy link
Copy Markdown
Contributor

The two-line --default=false assertion is the right test (the gum stub previously swallowed the flag). Production already has gum confirm --default=false.

Heads-up: #11000 rewrites test/shell.d/hermes-remove-test.sh (launcher-entry cases). This patch will conflict if it lands second. Fold the grep into #11000 after that merges, or rebase this onto it. Not worth a competing PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants